home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
verif33.zip
/
VERITEXT.DOC
< prev
next >
Wrap
Text File
|
1992-06-14
|
3KB
|
121 lines
VERITEXT.EXE: A Language conversion utility for
The Registration & Verification Door
for Version 3.3+
By Lance W. Williams
Kadet PCBoard
Camden, NY
(315) 245-3815
USR Dual Standard
If you wish to convert the door language file to an alternate
language, you can use the VERIFIER.ENG text file as a guide to what the
prompts are in each line. The following files are needed for
converting to additional language files and are included in the
archive::
VERIFIER.ENG: English text version of the text lines
VERITEXT.EXE: Converter to convert the ASCII to the Random Access File
VERITEXT. : The converted English text file, ready for the door
To create an alternate language file, copy the VERIFIER.ENG file
to a file called VERIFIER.<Lang. Ext.> and then translate the English
text to the language of your choice. Then use VERITEXT.EXE to create
the file that the VERIFIER door uses.
The VERITEXT.EXE program takes no parameters. It prompts you for
the file to read and the extension of the file to write (Just the 3
character extension, not the whole name or the ".") Also, the
extensions have to be the same as used by PCBoard!!
Notes on Editing the language files:
1: Most entries are limited to 75 characters per line. The following
are less than that:
Line Numbers Maximum Characters
23, 24, 25, 26, 64 33 characters maximum
32, 65 34 characters maximum
49, 50, 51 45 characters maximum
When editing, be sure to keep within these limits!
2: Some lines go together as a group, making a paragraph. These
groups are as follows:
Group 1: 19, 20, 21 (closing screen)
Group 2: 27, 28, 29 (mailing label formats)
Group 3: 35, 36 (address information entry)
Group 4: 37, 38 (regular mailings definitions)
Group 5: 41, 42, 43 (improper address warning)
Group 6: 66, 67, 68 (sysop verification message)
Any of these groups can have a sentence overlapping to the next
line (except for the last line in the group, of course) to fit the
length restrictions. Since they are all in a paragraph, the user
will not know the difference.
3: There is a bug in the DOORSOURCE handling of the @macro@ variable
that requires you to put an extra space AFTER any @macro@, since it
seems to strip the next character from the string along with the
macro. This additional space will not be shown to the caller. As
far as I know, all PCB @macro@'s are supported by the door now,
both in display text files, and in the VERITEXT prompts. Probably
even in the script questionnaires, since they use the same routines
to send the string.